Skip to content

Prepare 2021 July Release [HLS 1.3.0] #2052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jul 30, 2021
Merged

Prepare 2021 July Release [HLS 1.3.0] #2052

merged 7 commits into from
Jul 30, 2021

Conversation

Ailrun
Copy link
Member

@Ailrun Ailrun commented Jul 29, 2021

CC: @jneira, @berberman, @pepeiborra, @isovector

Resolves partially: #1990.

Copy link
Member

@jneira jneira left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is nice to see all merged prs at once
Many thanks for take care of release, including version bumps! ❤️

@jneira
Copy link
Member

jneira commented Jul 29, 2021

Resolves partially: #1990.

why partially?

@Ailrun
Copy link
Member Author

Ailrun commented Jul 29, 2021

@jneira Because this PR itself does not finish the release process, as there are more things like making sure binary builds well, GHCUp coordination, Hackage release, ...

@jneira
Copy link
Member

jneira commented Jul 29, 2021

Yeah, the pr is the starting point. Your plan is make the hackage release close to the github one?

@Ailrun
Copy link
Member Author

Ailrun commented Jul 29, 2021

Yes, I think managing single-release-related things in a single issue is better for modularity


- Binaries for GHC 9.0.1 are added by @anka-213.
- Call hierarchy plugin is added, contributed by @July541.
![hierarchy](https://user-images.githubusercontent.com/12473268/127550041-094151a6-be7b-484a-bb82-c61f326ca503.gif)
Copy link
Member Author

@Ailrun Ailrun Jul 29, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I notice just now that call hierarchy does not work when executing it on a type signature. Is this intended, @July541?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, reference other languages' implementations, it doesn't belong to call hierarchy I think.

@jneira
Copy link
Member

jneira commented Jul 29, 2021

I started to work in a gh job to automate the hackage release, i hope i will able to finish it some day 😅

https://github.com/jneira/haskell-language-server/blob/hackage-release/.github/workflows/hackage.yml

Ailrun and others added 2 commits July 29, 2021 17:31
Co-authored-by: Sandy Maguire <sandy@sandymaguire.me>
Co-authored-by: Sandy Maguire <sandy@sandymaguire.me>
ChangeLog.md Outdated
- `:info` command is added by @akrmn.
- The plugin uses the same default language as GHCi with @fmehta's patch.
- Wingman, where most changes owing to @isovector
- An option for disabling proof state styling is added.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- An option for disabling proof state styling is added.
- Wingman no longer changes the fixity of function definitions.
- Wingman now gives unique names to the holes it generates.
- Significant improvements in Wingman's ability to reason about polymorphic and GADT types.
- Wingman no longer suggests homomorphic destructs when the codomain is larger than the domain.
- "Complete case constructors" support for empty lambda cases
- Wingman will now give a warning if it ran out of gas during "attempt to fill hole"
- Metaprogramming improvements, including symbolic-name support, and the `pointwise` combinator.
- Fixed a bug when attempting to introduce too many variables in an `intros` metaprogram.

Copy link
Member Author

@Ailrun Ailrun Jul 29, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May I ask why you want to remove the line for proof state styling option?

Besides that,

  • Fixed a bug when attempting to introduce too many variables in an intros metaprogram.

should this be highlighted?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May I ask why you want to remove the line for proof state styling option?

it's the least interesting thing in the change, imo. does anyone even know what a proof state is?

Copy link
Collaborator

@isovector isovector left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm! thanks for tackling this, @Ailrun !

@July541
Copy link
Collaborator

July541 commented Jul 30, 2021

I'm confused why not release LSP first? LSP has update about ghc 9.0 and call hierarchy, in case we can remove at least the depencency in cabal.project.

@jneira
Copy link
Member

jneira commented Jul 30, 2021

we can make the release in GitHub and upload binaries cause the build uses the cabal.project
But thanks to note it, cause we can't do the hackage release without having all dependencies in hackage as well

@Ailrun Ailrun added the merge me Label to trigger pull request merge label Jul 30, 2021
@mergify mergify bot merged commit e7c5e90 into haskell:master Jul 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge me Label to trigger pull request merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants